It could happen likely with TMS320C2834x series since its code size is normally much bigger than that of other MCU series. Why? It's because it takes long long time to initialize variables in c_int00 routine and therefore after some time watch-dog makes unintentional reset to MCU. To prevent watch-dog reset during c_int00 routine operation, it is strongly recommended the entry point is set to the 'code_start' label (in TI's DSP28x_CodeStartBranch.asm) with watch-dog disabled. This is done by linker option -e in the project build options, that is, -ecode_start.
* Operating XDS100 together with easyDSP ?
XDS100v1 (TI or 3rd parties emulator) supports multiple FTDI devices only for CCS v4. Therefore when you use XDS100v1 with CCS v3.3, easyDSP can’t be used together.
* If
you use other SCI ports than easyDSP recommends to use
?
For example, easyDSP recommends to use GPIO28, 29 for SCIRXDA and SCITXDA respectively when SCI-communicating with F28335. If you use GPIO36 and GPIO35 instead, you will face the booting failure. It's because TI does not support serial booting via these pins (GPIO36 and 35).
* What if MCU is at the reset during easyDSP communication ?
It depends. If the boot mode after the reset is flashrom booting, then the MCU will boot again with the flashrom. If the boot mode after the reset is RAM booting, then MCU will boot with the serial data which easyDSP send for communication. It finally causes fatal error and can damage your system.